Skip to content

Conversation

@lgritz
Copy link
Collaborator

@lgritz lgritz commented Jan 17, 2025

I think this stems from libclang (doing the C preprocessing step for us) giving us relative paths on all platforms but Windows, where it gives absolute paths -- with backslaches and C:\ and all.

I'm going to be conservative and not switch to relative paths accross the board on Windows, but for now just restrict it to the builds we do for CI, in order to make the related tests pass for Windows on our CI (where we obviously don't want to have the reference output need to bake in absolute paths of the place they may happen to execute on the GHA runners).

I think this stems from libclang (doing the C preprocessing step
for us) giving us relative paths on all platforms but Windows,
where it gives absolute paths -- with backslaches and C:\ and all.

I'm going to be conservative and not switch to relative paths accross
the board on Windows, but for now just restrict it to the builds we do
for CI, in order to make the related tests pass for Windows on our CI
(where we obviously don't want to have the reference output need to
bake in absolute paths of the place they may happen to execute on the
GHA runners).

Signed-off-by: Larry Gritz <[email protected]>
@lgritz
Copy link
Collaborator Author

lgritz commented Jan 23, 2025

ping

@lgritz
Copy link
Collaborator Author

lgritz commented Jan 25, 2025

No objections for more than a week -> merging

@lgritz lgritz merged commit 121638e into AcademySoftwareFoundation:main Jan 25, 2025
23 checks passed
@lgritz lgritz deleted the lg-preprodeps branch January 25, 2025 16:47
continue; // skip pseudo files
if (dep == filename)
continue; // skip this file, since we already put it first
#if defined(_WIN32) && defined(OSL_CI)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A bit lite, but I'm not sure this actually works right now? There's an OSL_CI environment variable, but no compile definition that I can see.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Like many such things, it's expressed as ${PROJ_NAME}_CI to preserve a big block of cmake script that I maintain in parallel between OIIO and OSL and this makes it a lot easier to diff and port improvements from one project to the other.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I missed that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants